home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
gt_power
/
jrsuperc.zip
/
JRSUPERC.TXT
Wrap
Text File
|
1988-12-11
|
8KB
|
227 lines
JRSUPERC.arc by Jim Rash, 004/000 11/23/88
(rev. 12/11/88 correct: JDNET will unarc "G" bags)
This is a HELP file intended to supplement documentation provided with
Paul Meiners' NMAIL??? and James Davis' JDNET.
Supercharging netmail may be accomplished by using either JDNET or
MBAGGER.
"SUPERCHARGE" WITH JDNET"
==========================
Supercharging netmail by using JDNET.EXE and is disussed below at
three levels. Each higher level accomplishes additional supercharging
and depends on use of the prior levels.
LEVEL 1
-------
JDNET /S will supercharge mailbags. This means that multiple "B"
bags destined for another node will be combined. At this level, only
SIMILAR bags will be combined. That is, multiple netmail "B" bags for
the same node will be combined and multiple echomail "B" bags of the
SAME echo will be combined.
This level of supercharging may be implemented at ANY time, and
requires no prior notice to any other node.
The instruction: JDNET /S is placed in your netmail batch prior to
MDRIVER being activated.
LEVEL 2
-------
This level requires a change to JD.CNF either by an editor or by using
JDNET and its "S" menu option.
The purpose of this level is to combine bags destined to DIFFERENT end
points for delivery to an intermediate hub. For example, if you have
message bags destined for 001/000 and 003/001 but your only call is
to HUB system 004/000 then you could supercharge those other bags in a
single bag to 004/000 with the following line in your JD.CNF:
SC=004/000 -> 001-003
Additionally, if you receive echos from 004/000 then you will probably
have echo "B" bags to deliver. These can be added to that single bag
by making the JD.CNF line as follows:
SC=004/000 -> 001-003,E00,E09,E10
This will cause any echo "B" bags for echos beginning E00, E09, or E10
and with ACCEPTS pointing to 004/000 as the primary to be
supercharged.
NOTE: Level 2 of supercharging requires that you confirm with the
destination (004/000 in the above example) that they are prepared to
receive this level of supercharging. The receiving node MUST run
JDNET /U prior to running MDIST. This will UN-arc the superbag to
what MDIST is expecting.
LEVEL 3
-------
This level generates a "Super Bag for a specified node that contains
not only "B" bags resulting from LEVEL 1 & 2 supercharging, but also
"E" bags that the destination has ASKED YOU to deliver to them..
This level is implememted by first inplementing Levels 1 & 2, and then
using JDNET menu option "E" to enter the destination node, each echo
number desired, and the julian date of the last bag sent for each
echo.
--for Destinations---
This level again requires coordination with the destination. In
addition to the destination running JDNET /U they must also modify
their ROUTING.BBS as described below.
CAUTION:
Since the echos will be received automatically, the "REQUEST ECHOMAIL
CONFERENCES" and "OUTBOUNDS" for echos should be removed.
In addition, there now needs to be a special routing file used by
MBAGGER only, that is different from the one used by MDRIVER.
Here is the reason.... Echo "B" bags destined upstream to the sponsor
should be supercharged to the person who send you the "Super Bags". If
MDRIVER finds an ACCEPT with the net/node of your source and has an
echo "B" bag that is not supercharged, then MDRIVER will automatically
generate a REQUEST when connected with the host. This will be done
not knowing that the echo will also be in a "Super Bag".
For simplicity, and as a DEFAULT, your ROUTING.BBS should contain all
information, including ACCEPT statements that point to the actual
source of the echos you receive. Let MBAGGER, JDNET, and MDIST
default to this ROUTING.BBS. This will properly bag, supercharge, and
unarc your mail bags.
The ROUTING file used by MDRIVER should then be named something such
as ROUT0400.BBS and your MDRIVER line points to it with the parameter
/R:ROUT0400.BBS. This routing will contain ACCEPTS for echos that are
superbagged to you, but with a DUMMY net/node, i.e. 001/999 that
appears in the nodelist, but is INBOUNDED in ALL your sessions.
(for example ACCEPT E00/001 -> 001/999 )
This will allow others to pick up echos and deliver "B" bags to you,
but you will not process those "B" bags to anyone upstream until you
have the opportunity to supercharge them using JDNET /S.
RECAP of SUPERCHARGE PROCEDURES
-------------------------------
LEVEL 1 - Combine SIMILAR "B" bags
-------
Sender: 1. Use JDNET /S before each MDRIVER.
Receiver: n/a
LEVEL 2 - Combine DIFFERENT "B" bags
-------
(incl. Level 1 requirement)
Sender: 2. Edit JD.CNF to create "SC=" lines.
MUST insure that Reciever is running /U.
Receiver: 3. MUST run JDNET /U before MDIST.
May run JDNET /U between multiple sessions.
LEVEL 3 - Include "E" bags as specified
-------
(incl. Level 2 requirements)
Sender: 4. Use JDNET menu option "E" to specify reciver net/node
and list echos to be SENT to receiver and the last
Julian date of each echo sent.
5. DO NOT forward a SUPER BAG to any other node. You
should deliver the bag direct.
Receiver: 6. Run JDNET /S /R:ROUTING.BBS
where ROUTING.BBS contains ACCEPTS with actual
sources.
6. Run MDRIVER ... /R:ROUT0400.BBS
a) where ROUT0400.BBS has "ECHO REQUESTS" and "echo
OUTBOUNDS" removed for those echos you now receive
via G-Bag.
b) where ACCEPTS have dummy node 001/999 for those same
echos.
BAG CONSOLIDATION WITH MBAGGER /G
=================================
Beginning with Paul Meiner's NMAIL190 it is possible to "consolidate"
bags into "G bags" using MBAGGER.
Before implementing consolidation, confirm this with the destination
node.
NO consolidation takes place at all unless a node is listed in the
"BAG CONSOLIDATION" section of the routing.bbs
When a node is listed, any ACCEPT or FORWARD pointing to that node
will be consolidated into a single bag.
If any ECHO conference is listed in "bag consolidation" after a node,
then that echo "E" bag will also be consolidated.
As with using JDNET to supercharge echo "E" bags, I strongly
recommend that if you do charge "E" bags that you either call the
destination direct or that they call you and that "G" bags containing
"E" bags NOT be dumped into the netmail flow.
CO-EXISTANCE
============
What happens if you receive BOTH "superbags" and "consolidated
G-Bags"? Depending on what systems the bags pass through it is
possible that you will receive a "G" bag that contains a "super bag".
JDNET will unarc a "G" bag, but I am not sure that MDIST will unarc a
"super B bag". I suggest that you keep the JDNET /U in your batch
files before MDIST.
ECHO SPONSORS
=============
Sponsors of echomail conferences should NOT bag their conferences more
than ONCE daily to create daily "E" bags.
If you bag your conference at noon, for example, it may be picked up
by a crash session and placed in the network. Should you later
receive more messages, place them in your message area and then bag
them the same day, they will be ADDED to the existing bag on your
system. However, a bog for that day will already be in circulation
minus those new messages.
If you wish to bag netmail and echo messages OTHER THAN YOUR OWN, then
you may specify an alternate routing.bbs that has your own conferences
removed from the MESSAGE DISTRIBUTION section. This will prevent the
premature bagging of your conference.
example: MBAGGER /R:NOTMINE.BBS
( MDIST should ALWAYS use a complete ROUTING.BBS )
NOTE: This echo help file is intended to supplement, not replace
documentation provided with the JD series of programs and GT NETMAIL
documentation.